I am not convinced that we should do this because it changes quite a few options and it can be disruptive to end users, specially given that, because of the declarative configuration, this may go in a different direction upstream and we want to stay aligned if possible.

@codeboten Is this fear unfounded? Searching I could find open-telemetry/opentelemetry-specification/issues/4440 which does mention keepalives explicitly, but I don't know how to think about this

CodSpeed Performance Report

Merging #14203 will degrade performances by 43.39%

_{Comparing mx-psi:mx-psi/poc-confighttp-keepalive (4462136) with main (b5aaf8e)}

Summary

❌ 4 regressions
✅ 69 untouched

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

I'm supportive of this approach. I think we can finalize the migration before marking confighttp 1.0

I'm supportive of this approach. I think we can finalize the migration before marking confighttp 1.0

Since the OTLP exporter and the OTLP receiver are marked as 1.0 I think we would not be able to complete this migration: we can deprecate the older options but we need to keep compatibility with them until a 2.0 version of these components.